Systems and methods for event admissions based on fingerprint recognition

ABSTRACT

Systems and methods for fingerprint recognition-based event admission are provided. A user may use a user device to purchase a ticket for an event and provide a fingerprint scanned on the user device to a fingerprint validation system. The fingerprint validation system may associate the purchased ticket with the user and store the fingerprint template associated with the user as a reference template. When the user arrives at an entrance of the event, the user may scan a fingerprint at a fingerprint scan device at the entrance. Fingerprint validation system may compare the received fingerprint template with stored fingerprint reference templates, validate that the user is associated with a purchased ticket, and grant access to the event.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/588,316, filed on Dec. 31, 2014; the disclosure of which isincorporated by reference herein.

BACKGROUND Field of the Invention

The present invention generally relates to biometrics and, moreparticularly, to using fingerprint recognition for admission to events.

Related Art

Various online ticket sellers provide websites through which parties canbuy and sell tickets online. These tickets can be obtained by a user toreserve seats and/or admission for a variety of events, such as sportingevents, concerts, theater events, and other entertainment events.Typically, a buyer looks for available tickets on a ticket marketplacewebsite or other online listing and decides which, if any, of theavailable tickets are of interest to the buyer for possible purchase.When a ticket is purchased and the ticketholder goes to the associatedevent, users typically present a physical ticket, such as a paperticket, for admission to the event.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an illustrative computing system that isadapted for implementing the selection and purchase of tickets and/orfingerprint recognition-based event admission according to anembodiment.

FIG. 2 is a block diagram of an illustrative computer system suitablefor implementing on one or more devices of the computing system in FIG.1 according to an embodiment.

FIG. 3 is a block diagram of an illustrative system for facilitatingevent admission using fingerprint recognition according to anembodiment.

FIG. 4 is a diagram of an illustrative event entrance showingfingerprint scan devices according to an embodiment.

FIG. 5 is a flowchart showing an illustrative process that may beperformed for using fingerprint recognition for event admissionaccording to an embodiment.

FIG. 6 is a flowchart showing an illustrative process that may beperformed for using remote fingerprint recognition for event admissionaccording to an embodiment.

DETAILED DESCRIPTION

Exemplary applications of systems and methods according to the presentinvention are described in this section. These examples are beingprovided solely to add context and aid in the understanding of theinvention. It will thus be apparent to one skilled in the art that thepresent invention may be practiced without some or all of these specificdetails. In other instances, well known process steps have not beendescribed in detail in order to avoid unnecessarily obscuring thepresent invention. Other applications are possible, such that thefollowing examples should not be taken as limiting.

In the following detailed description, references are made to theaccompanying drawings, which form a part of the description and in whichare shown, by way of illustration, specific embodiments of the presentinvention. Although these embodiments are described in sufficient detailto enable one skilled in the art to practice the invention, it isunderstood that these examples are not limiting, such that otherembodiments may be used, and changes may be made without departing fromthe spirit and scope of the invention.

Devices, systems, and methods are provided for performing activitiesrelated to online ticket sale, online ticket purchase, and ticketlessevent admission using fingerprint recognition. In various particularembodiments, the devices, systems, or methods can involve one or moredevices in communication over a network. Such devices, systems, andmethods can facilitate fingerprint recognition for event admission.

While the various examples disclosed herein focus on particular aspectsregarding the online sale of tickets, online purchase of tickets, and/orfingerprint recognition-based admission to ticketed events, it will beunderstood that the various inventive principles and embodimentsdisclosed herein can be applied to other types of ticketed applicationsand arrangements as well. For example, a ticket purchase that isperformed in person or on a closed or proprietary computing system mayutilize one or more of the aspects and features found in the varioussystems and methods provided.

Reference throughout the specification to “various embodiments,” “someembodiments,” “one embodiment,” “an embodiment,” “various examples,”“one example,” “an example,” or “some examples” means that a particularfeature, structure, or characteristic described in connection with theembodiment or example is included in at least one embodiment. Thus,appearances of these are not necessarily all referring to the sameembodiment. Furthermore, the particular features, structures, orcharacteristics may be combined in any suitable manner in one or moreembodiments.

The present disclosure provides systems and methods for ticketless eventadmission using fingerprint recognition. The systems and methodsdescribed provide enhanced user experience when going to events becauseusers no longer need to carry tickets or other forms of identificationor authentication. Events may include social, recreational, orentertainment events, such as concerts, musicals, shows, fairs,amusement parks, sporting events, and the like. Alternatively, eventsmay include business related events, such as business meetings,conferences, retreats, and the like.

In various embodiments, a service provider may provide tickets for salethrough a website or an application associated with the serviceprovider. A service provider server associated with the service providermay maintain a database containing information relating to events andtickets for the events. The service provider may provide fingerprintrecognition-based event admission services via the service providerserver.

A user may use a user device to buy a ticket for an event via theservice provider server. The user may use the user device to scan his orher fingerprint and transmit fingerprint data (e.g., a fingerprintsample, a fingerprint sample, etc.) to the service provider before, atthe time of, or after purchasing the ticket. The service provider servermay receive the fingerprint data and store the fingerprint data in afingerprint template database on a hardware storage drive of the serviceprovider server. The service provider server may associate thefingerprint data with a user account of the user and/or the ticketpurchase transaction.

When the user arrives at an entrance for the event, the user may scanhis or her fingerprint at a fingerprint scan device at the entrance andenter the event without providing other information. When the user scanshis or her finger, the fingerprint scan device may transmit fingerprintdata to the service provider server. The service provider server may usethe fingerprint data received from the fingerprint scan device toidentify the user and/or authenticate the user based on comparing thereceived fingerprint data with fingerprint data stored in thefingerprint template database. Thus, the user can enter the eventconveniently without carrying a ticket or other forms of verification.

In various embodiments, the user device or the fingerprint scan devicesenses and/or scans a fingerprint to capture a fingerprint sample, whichmay be an image of a fingerprint. The user device, the fingerprint scandevice, or the service provider server may process the fingerprintsample to generate a fingerprint template, which includes relevantfeatures and/or characteristics extracted from the fingerprint sample.Relevant features/characteristics may include, for example, patterns(e.g., characteristics of ridges) and/or minutia points (e.g. uniquefeatures within the patterns.

In various embodiments, the service provider server may compare afingerprint template that is based on a fingerprint scan on thefingerprint scan device or the user device with reference fingerprinttemplates stored in the fingerprint template database. The referencefingerprint templates may include a fingerprint template of the userthat is based on a previous fingerprint scan on the user device, forexample, when purchasing the ticket.

Advantageously, the user does not have to train the fingerprint scandevice, in a process called “enrollment,” by providing a fingerprintscan to the fingerprint scan device because a reference template for theuser based on a fingerprint scan on the user device is previously storedin the fingerprint template database. Accordingly, the user mayconveniently go to the fingerprint scan device at an entrance for anevent without a physical ticket or authenticating information even if itis the user's first time using the fingerprint recognition-based eventadmission services provided by the service provider.

Beginning with FIG. 1, an exemplary embodiment of a computing systemadapted for implementing the selection and purchase of tickets and/orfingerprint recognition-based event admission is illustrated in blockdiagram format. As shown, a computing system 100 may comprise orimplement a plurality of servers and/or software components that operateto perform various methodologies in accordance with the describedembodiments. Exemplary servers may include, for example, stand-alone andenterprise-class servers operating a server OS such as a MICROSOFT® OS,a UNIX® OS, a LINUX® OS, or other suitable server-based OS. It can beappreciated that the servers illustrated in FIG. 1 may be deployed inother ways and that the operations performed and/or the servicesprovided by such servers may be combined or separated for a givenimplementation and may be performed by a greater number or fewer numberof servers. One or more servers may be operated and/or maintained by thesame or different entities.

Computing system 100 can include, among various devices, servers,databases, and other elements, a client 102 that may comprise or employone or more client devices 104, such as a laptop, a mobile computingdevice, a personal computer (PC), and/or any other computing devicehaving computing and/or communications capabilities in accordance withthe described embodiments. In particular, it is specificallycontemplated that client devices 104 can include a smartphone, acellular telephone, or other mobile device that a user can carry on orabout his or her person and access readily.

Client devices 104 generally may provide one or more client programs106, such as system programs and application programs to perform variouscomputing and/or communications operations. Exemplary system programsmay include, without limitation, an operating system (e.g., MICROSOFT®OS, UNIX® OS, LINUX® OS, Symbian OS™ Embedix OS, Binary Run-timeEnvironment for Wireless (BREW) OS, JavaOS, a Wireless ApplicationProtocol (WAP) OS, and others), device drivers, programming tools,utility programs, software libraries, application programming interfaces(APIs), and so forth. Exemplary application programs may include,without limitation, a web browser application, messaging applications(e.g., e-mail, instant messaging (IM), short message service (SMS),multimedia messaging service (MMS), telephone, voicemail, voice overinternet protocol (VoIP), video messaging, etc.), contacts application,calendar application, electronic document application, databaseapplication, media application (e.g., music, video, television),location-based services (LBS) application (e.g., global positioningsystem (GPS), mapping, directions, point-of-interest, locator, etc.),and so forth. One or more of client programs 106 may display variousgraphical user interfaces (GUIs) to present information to and/orreceive information from one or more of client devices 104.

As shown, client 102 can be communicatively coupled via one or morenetworks 108 to a network-based system 110. Network-based system 110 maybe structured, arranged, and/or configured to allow client 102 toestablish one or more communications sessions with network-based system110 using various computing devices 104 and/or client programs 106.Accordingly, a communications session between client 102 andnetwork-based system 110 (e.g., a communications session fortransmitting fingerprint data, such as a fingerprint sample or afingerprint template) may involve the unidirectional and/orbidirectional exchange of information and may occur over one or moretypes of networks 108 depending on the mode of communication. While theembodiment of FIG. 1 illustrates a computing system 100 deployed in aclient-server operating environment, it is to be understood that othersuitable operating environments and/or architectures may be used inaccordance with the described embodiments.

Data and/or voice communications between client 102 and thenetwork-based system 110 may be sent and received over one or morenetworks 108 such as the Internet, a wide area network (WAN), a wirelesswide area network (WWAN), a local area network (LAN), a wireless localarea network (WLAN), a mobile telephone network, a landline telephonenetwork, a VoIP network, as well as other suitable networks. Forexample, client 102 may communicate with network-based system 110 overthe Internet or other suitable WAN by sending and or receivinginformation via interaction with a web site, e-mail, 1M session, and/orvideo messaging session. Any of a wide variety of suitable communicationtypes between client 102 and system 110 can take place, as will bereadily appreciated. In particular, wireless communications of anysuitable form may take place between client 102 and system 110, such asthat which often occurs in the case of mobile phones or other personalmobile devices.

Network-based system 110 may comprise one or more communications servers120 to provide suitable interfaces that enable communication usingvarious modes of communication and/or via one or more networks 108.Communications servers 120 can include a web server 122, an API server124, and/or a messaging server 126 to provide interfaces to one or moreapplication servers 130. Application servers 130 of network-based system110 may be structured, arranged, and/or configured to provide variousonline marketplace, ticket fulfillment services, and/or fingerprintrecognition services to users that access network-based system 110. Invarious embodiments, client 102 may communicate with applicationsservers 130 of network-based system 110 via one or more of a webinterface provided by web server 122, a programmatic interface providedby API server 124, and/or a messaging interface provided by messagingserver 126. It can be appreciated that web server 122, API server 124,and messaging server 126 may be structured, arranged, and/or configuredto communicate with various types of client devices 104 and/or clientprograms 106 and may interoperate with each other in someimplementations.

Web server 122 may be arranged to communicate with web clients and/orapplications such as a web browser, web browser toolbar, desktop widget,mobile widget, web-based application, web-based interpreter, virtualmachine, and so forth. API server 124 may be arranged to communicatewith various client programs 106 comprising an implementation of API fornetwork-based system 110. Messaging server 126 may be arranged tocommunicate with various messaging clients and/or applications such ase-mail, IM, SMS, MMS, telephone, VoIP, video messaging, and so forth,and messaging server 126 may provide a messaging interface to enableaccess by client 102 to the various services and functions provided byapplication servers 130.

When implemented as an online ticket marketplace, application servers130 of network-based system 110 may provide various online marketplaceand ticket fulfillment services including, for example, accountservices, buying services, selling services, listing catalog services,delivery services, payment services, gathering services, andnotification services. Application servers 130 may include an accountserver 132, a selling server 134, a buying server 136, a listing catalogserver 138, a dynamic content management server 140, a payment server142, a notification server 144, and/or a delivery server 146 structuredand arranged to provide such online marketplace and ticket fulfillmentand/or redistribution services.

Application servers 130, in turn, may be coupled to, and capable ofaccessing, one or more databases 150 including a subscriber database152, an active events database 154, and/or a transaction database 156.Databases 150 generally may store and maintain various types ofinformation for use by application servers 130, and may comprise or beimplemented by various types of computer storage devices (e.g., servers,memory) and/or database structures (e.g., relational, object-oriented,hierarchical, dimensional, network) in accordance with the describedembodiments.

Continuing with FIG. 2, an exemplary computer system 200 suitable forimplementing on one or more devices, servers, and systems in FIG. 1and/or FIG. 3 is depicted in block diagram format. In variousimplementations, a device that includes computer system 200 may comprisea personal computing device (e.g., a smart or mobile phone, a wearablecomputing device, such as glasses or a smart watch, a computing tablet,a personal computer, laptop, PDA, Bluetooth device, key FOB, badge,etc.) that is capable of communicating with a network. A serviceprovider, such as a ticket provider and/or a payment provider, mayutilize a network computing device (e.g., a network server) thatincludes computer system 200 capable of communicating with the network.It should be appreciated that each of the devices utilized by users,venues, and/or service providers may be implemented as computer system200 in a manner as follows.

Computer system 200 can include a bus 202 or other communicationmechanism for communicating information data, signals, and informationbetween various components of computer system 200. Components include aninput/output (I/O) component 204 that processes a user action, such asselecting keys from a keypad/keyboard, selecting one or more buttons orlinks, etc., and sends a corresponding signal to bus 202. I/O component204 may also include an output component, such as a display 211 and acursor control 213 (such as a keyboard, keypad, mouse, etc.). Anoptional audio input/output component 205 may also be included to allowa user to use voice for inputting information by converting audiosignals. Audio I/O component 205 may allow the user to hear audio. Atransceiver or network interface 206 transmits and receives signalsbetween computer system 200 and other devices, such as a user device, amerchant server, a venue server, a payment provider server, and/or aservice provider server via a network 260. In various embodiments, suchas for many cellular telephone and other mobile device embodiments, thistransmission can be wireless, although other transmission mediums andmethods may also be suitable. A processor 212, which can be amicro-controller, digital signal processor (DSP), or other processingcomponent, processes these various signals, such as for display oncomputer system 200 or transmission to other devices over network 260via a communication link 218. Again, communication link 218 can simplybe a wireless communication form in some embodiments. Processor 212 mayalso control transmission of information, such as cookies or IPaddresses, to other devices.

Components of computer system 200 also include a system memory component214 (e.g., RAM), a static storage component 216 (e.g., ROM), and/or adisk drive 217. Computer system 200 performs specific operations byprocessor 212 and other components by executing one or more sequences ofinstructions contained in system memory component 214. Logic may beencoded in a computer readable medium, which may refer to any mediumthat participates in providing instructions to processor 212 forexecution. Such a medium may take many forms, including but not limitedto, non-volatile media, volatile media, and transmission media. Invarious implementations, non-volatile media includes optical or magneticdisks, volatile media includes dynamic memory, such as system memorycomponent 214, and transmission media includes coaxial cables, copperwire, and fiber optics, including wires that comprise bus 202. In oneembodiment, the logic is encoded in non-transitory machine-readablemedium. In one example, transmission media may take the form of acousticor light waves, such as those generated during radio wave, optical, andinfrared data communications.

Some common forms of computer readable media includes, for example,floppy disk, flexible disk, hard disk, magnetic tape, any other magneticmedium, CD-ROM, any other optical medium, punch cards, paper tape, anyother physical medium with patterns of holes, RAM, PROM, EPROM,FLASH-EPROM, any other memory chip or cartridge, or any other mediumfrom which a computer is adapted to read.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by computer system 200. In various other embodiments of thepresent disclosure, a plurality of computer systems 200 coupled bycommunication link 218 to network 260 (e.g., such as a LAN, WLAN, PTSN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another. Modules described herein can be embodied in one ormore computer readable media or be in communication with one or moreprocessors to execute or process the steps described herein.

A computer system may transmit and receive messages, data, information,and instructions, including one or more programs (i.e., applicationcode), through a communication link and a communication interface.Received program code may be executed by a processor as received and/orstored in a disk drive component or some other non-volatile storagecomponent for execution.

Where applicable, various embodiments provided by the present disclosuremay be implemented using hardware, software, or combinations of hardwareand software. Also, where applicable, the various hardware componentsand/or software components set forth herein may be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein may be separated into sub-components comprising software,hardware, or both without departing from the scope of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components may be implemented as hardware components andvice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Suchsoftware may be stored and/or used at one or more locations along orthroughout the system, at client 102, network-based system 110, or both.Where applicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The foregoing networks, systems, devices, servers, and numerousvariations thereof can be used to implement a fingerprint recognitionoperation during admission to a purchased-access event.

FIG. 3 is a block diagram 300 showing a fingerprint recognition-basedadmission system that may be used to store reference fingerprinttemplates associated with users, associate purchased tickets with users,compare a fingerprint template with reference fingerprint templates,validate that a user is associated with a purchased ticket for an event,and grant access to the event according to an embodiment. As shown inFIG. 3, the fingerprint recognition-based admission system may include avenue server or device 310, a user device 320, a service provider server330, and/or a fingerprint validation system 360.

In some embodiments, a venue device such as a venue device 310(sometimes referred to herein as a venue server or a venue system) canbe present at each of a plurality of different event venues (e.g.,stadiums, theaters, arenas, amphitheaters, airplanes, cruise ships,hotels, or other venues at which ticketed events are held or for whichaccess to restricted portions of the venue can be purchased for a periodof time). Venue server 310 can provide information regarding eventsscheduled to occur at a particular venue and regarding seating and/orother accommodations (e.g., hotel rooms, cruise ship cabins, etc.) atthat venue. In some embodiments, venue server 310 can provide theinformation to service provider server 330. Service provider server 330can obtain information regarding events scheduled to occur at variousvenues and information regarding seating and/or other accommodations atthe various venues from one or more venue devices (servers) 310, fromother sources, or service provider server 330 may have a database ofevent information and venue information independent of any interactionwith a venue device. Service provider server 330 may, for example, be animplementation of system 110 of FIG. 1.

Venue server 310 can be a system that includes one or more computers,one or more servers, one or more computing tablets, one or more mobiledevices, communications equipment, one or more devices configured toscan fingerprints and/or other suitable computing equipment, asexamples. Venue device 310 can have processing circuitry such as aprocessor 312 and storage such as a memory 311. Venue device 310 may,according to some embodiments, include one or more fingerprint scandevices such as one or more fingerprint scan devices 314 andcommunications equipment such as a communications module 316.

Processor 312 can execute a software program stored in memory 311 forproviding information regarding events scheduled to be at the venue,regarding seating at the venue, or other information for each scheduledor ongoing event. Venue device 310 can provide the information to theservice provider server and/or to a user device such as user device 320.

Fingerprint scan device 314 may scan a fingerprint of a user, create afingerprint sample based on the scan, and/or process the fingerprintsample by extracting features to generate a fingerprint template.Fingerprint scan device 314 may be a computer, a computing tablet, or amobile device configured to scan a fingerprint of users, as examples.Alternatively, fingerprint scan device 314 may be a specialized devicefor scanning fingerprints, or integrated with automated entrances gates,such as automated turnstile entrance gates.

Communication module 316 may include a DSL (e.g., Digital SubscriberLine) modem, a PSTN (Public Switched Telephone Network) modem, anEthernet device, a broadband device, a satellite device and/or variousother types of wired and/or wireless network communication devicesincluding microwave, radio frequency, infrared, Bluetooth, and nearfield communication (NFC) devices. Fingerprint scan device 314 mayutilize communications circuitry such as communication module 316 tocommunicate with user device 320, service provider server 330, and/orfingerprint validation system 360. In various embodiments, fingerprintscan devices 314 may be operated by the venue, by a service providerserver, or by another service such as a payment provider.

Venue device 310 can be disposed at the venue. However, this is merelyillustrative. If desired, venue device 310 can be disposed at a locationother than the venue. Each venue can have a dedicated venue device 310or a plurality of different venues can share a common venue device 310.For example, co-owned venues can share a common venue device 310.

In some embodiments, venue device 310 can be omitted if one or morefingerprint scan devices at venues are provided by a service provider ora third-party.

A user (e.g., an event attendee) can use a device such as user device320 to shop online for available tickets and/or provide his or herfingerprint data (e.g., a fingerprint sample, a fingerprint template,etc.). User device 320 can be a mobile device such as a cellulartelephone, a tablet computer, a laptop computer, or another portablecomputing device. User device 320 can be a non-mobile device such as ahome (land line) telephone, a desktop computer, an interactive set topbox, or the like. User device 320 can be any device or combination ofdevices that facilitate viewing, selection, and purchasing of onlinetickets, and/or scanning a fingerprint and transmitting fingerprintdata. User device 320 may, for example, be an implementation of clientdevice 104 of FIG. 1.

User device 320 can have a processor 321, a memory 322, a globalpositioning system component (GPS) 323, fingerprint scan module 324,and/or other suitable device components. Fingerprint scan module 324 maybe integrated as a part of user device 320 and configured to scan afingerprint. Alternatively, fingerprint scan module 324 may be aseparate hardware unit that can be coupled to user device 320 viawireless or wired communication. Processor 321 can execute anapplication such as an app 325 that facilitates ticket selection,purchase, and/or fingerprint recognition-based event admission methodsdisclosed herein. App 325 can be stored in a memory 322. App 325 canprovide a graphical user interface (GUI) for the user when the user isselecting and purchasing tickets. If desired, app 325 can be a dedicatedticket purchasing and fingerprint scanning app. However, this is merelyillustrative. In some configurations, app 325 can be part of anotherapp, such as a PayPal, Inc. payment provider app.

User device 320 can communicate with venue device 310, service providerserver 330, and/or fingerprint validation system 360 via a network suchas the Internet 340. User device 320 can communicate with Internet 340via either a wired connection or a wireless connection. App 325 may beconfigured to transmit fingerprint data (e.g., a fingerprint sample, afingerprint template, etc.) to service provider server 330 and/orfingerprint validation system 360. For example, service provider server330 may have access to fingerprint data for a user based on fingerprintdata from fingerprint scan module 324. Further, app 325 may beconfigured to transmit to service provider server 330 locationinformation of user device 320. For example, service provider server 330may have access to location information for a user based on locationdata from GP S 323.

Service provider server 330 may be operated by an online ticket sellersuch as StubHub, Inc. Service provider server 330 may facilitate onlineticket sales and/or fingerprint recognition-based event admission.Service provider server 330 may include processing circuitry such as aprocessor 331 in communication with storage such as a memory 332.Processor 331 can include one or more processors. Processor 331 canaccess accounts such as a user account in a user database 333 and/or avenue account in a venue database 334 that are stored in memory 332. Auser account can include information regarding the user (e.g.,identification information, preferences, account numbers, purchasehistory, purchased-ticket event information, attended event information,etc.). A venue account can include information regarding the venue(e.g., information regarding events, seating, venue location, and othervenue features). Memory 332 can be separate from the service providerserver 330 and can be used to store any number of user accounts andvenue accounts. Memory 332 can be distributed, e.g., have portionsthereof disposed at a plurality of different locations. Other accountsmay also be accessible by processor 331, such as accounts of usersselling tickets that include ticket details, such as price, quantity,location, and event information, and financial information that enablefunds to be deposited into seller accounts when their tickets are sold.

Service provider server 330 may include one or more servers located atone or more locations. Thus, the service provider server 330 can begeographically and operationally distributed if desired. Serviceprovider server 330 can be part of another system, such as a paymentprovider system or a fingerprint recognition-based event admissionsystem. Service provider server 330 may include another system, such asfingerprint validation system 360. Service provider server 330 cancommunicate with venue device 310 over a wired or wireless connectionsuch as via a network such as Internet 340. Service provider server 330can communicate with a plurality of different venue devices 310. Venuedevice 310 can communicate with a plurality of different serviceprovider servers 330. A plurality of different service provider servers330 can communicate among themselves and can be considered herein asbeing the same as a single service provider server 330, A user canoperate user device 320 to interact with service provider server 330 sothat the user can select, purchase, and/or sell tickets. The user canoperate user device 320 and/or fingerprint scan device 314 to scan afingerprint and send fingerprint data to service provider server 330and/or fingerprint validation system 360

Service provider server 330 can communicate with venue device 310 toobtain information about the venue. For example, service provider server330 can communicate with venue device 310 to obtain informationregarding the scheduling of events at the venue and regarding featuresof the venue. The features of the venue can be dependent upon the eventsof the venue, e.g., the features of the venue can vary from event toevent. Generally, venue device 310, user device 320, and serviceprovider server 330 can perform functions discussed herein. That is, atleast to some extent, a function that is discussed herein as beingperformed via a particular one of these devices can be performed by adifferent one of these devices, by a combination of these devices,and/or by other devices.

Fingerprint validation system 360 may include a fingerprint associationmodule 362, a ticket association module 364, a notification module 365,a comparison module 366, a validation or authentication module 368, anaccess module 370, a network interface module 372, and a storage module374. Any or all of the modules may be implemented as a subsystem offingerprint validation system 360 including a circuit, a hardwarecomponent, a hardware subcomponent, and/or a variety of other subsystemsknown in the art. Furthermore, any or all of the modules may bepreconfigured to perform their disclosed functionality, or may beconfigured by a processing system “on-the-fly” or as needed to performtheir disclosed functionality. As such, any or all of the modules mayinclude preconfigured and dedicated circuits and/or hardware components,or may be circuits and/or hardware components that are configured asneeded.

For example, any or all of the modules may be provided via one or morecircuits that include resistors, inductors, capacitors, voltage sources,current sources, switches, logic gates, registers, and/or a variety ofother circuit elements known in the art. One or more of the circuitelements in a circuit may be configured to provide the circuit(s) thatcause the modules to perform the functions described below. As such, insome embodiments, preconfigured and dedicated circuits may beimplemented to perform the functions of the modules. In otherembodiments, a processing system may execute instructions on anon-transitory, computer-readable medium to configure one or morecircuits as needed to perform the functions of the modules.

Fingerprint association module 362 may be included as a separate moduleprovided in fingerprint validation system 360, or may be provided usinginstructions stored on a computer-readable medium that, when executed bya processing system in fingerprint validation system 360, configurefingerprint association module 362 to store a fingerprint template of auser as a reference fingerprint template associated with the user, aswell as provide any of the other functionality that is discussed herein.In an embodiment, fingerprint association module 362 may include afeature extractor module configured to extract features from afingerprint sample (e.g., a scanned fingerprint image) received fromuser device 320, and a template generator module configured to generatea fingerprint template (e.g., fingerprint data indicating relevantfeatures and/or characteristics) using the extracted features. Relevantfeatures that are extracted from the fingerprint sample may include, forexample, patterns (e.g., characteristics of ridges) and/or minutiapoints (e.g. unique features within the patterns). In other embodiments,the feature extractor module and the template generator module may beincluded in user device 320, and fingerprint association module 362 mayreceive a fingerprint template from user device 320.

Ticket association module 364 may be included as a separate moduleprovided in fingerprint validation system 360, or may be provided usinginstructions stored on a computer-readable medium that, when executed bya processing system in fingerprint validation system 360, configureticket association module 364 to associate a user with a purchasedticket to an event in response to the user purchasing the ticket, aswell as provide any of the other functionality that is discussed herein.

Notification module 365 may be included as a separate module provided infingerprint validation system 360, or may be provided using instructionsstored on a computer-readable medium that, when executed by a processingsystem in fingerprint validation system 360, configure notificationmodule 365 to send a notification to user device 320 that includes arequest for approval and/or validation by providing a fingerprint scanon the user device 320, as well as provide any of the otherfunctionality that is discussed herein.

Comparison module 366 may be included as a separate module provided infingerprint validation system 360, or may be provided using instructionsstored on a computer-readable medium that, when executed by a processingsystem in fingerprint validation system 360, configure comparison module366 to compare a fingerprint template of a user with referencefingerprint templates, as well as provide any of the other functionalitythat is discussed herein. In an embodiment, comparison module 366 mayinclude a matcher module configured to generate a matching score basedon comparing the fingerprint template of the user with one or more ofthe reference fingerprint templates.

Validation module 368 may be included as a separate module provided infingerprint validation system 360, or may be provided using instructionsstored on a computer-readable medium that, when executed by a processingsystem in fingerprint validation system 360, configure validation module368 to validate that a user is associated with a purchased ticket basedon a comparison by comparison module 366, as well as provide any of theother functionality that is discussed herein. Validation module 368 mayvalidate the user by identifying the user and/or authenticating the useras a purchaser of a ticket to an event based on the matching score (e.g.a matching score being above a predetermined threshold, which may beset, for example, by the service provider).

Access module 370 may be included as a separate module provided infingerprint validation system 360, or may be provided using instructionsstored on a computer-readable medium that, when executed by a processingsystem in fingerprint validation system 360, configure access module 370to grant access to a user in response to validation by validation module368 by, for example, transmitting an access granting signal (e.g.,access granting data packet) to an automated entrance gate, as well asprovide any of the other functionality that is discussed herein.

Network interface module 372 is communicatively coupled to network suchas Internet 340, and may be communicatively coupled to any or all ofmodules 362, 364, 366, 368, and/or 370, any of which may be coupled to astorage module 374. Network interface module 372 may be included as aseparate module provided in fingerprint validation system 360, or mayinclude communications hardware (e.g., antennas) and instructions storedon a computer-readable medium that, when executed by a processing systemin fingerprint validation system 360, configure network interface module372 to operate the communications hardware to send and receive dataand/or information over Internet 340, as well as provide any of theother functionality that is discussed herein.

Storage module 374 may include one or more databases, such as a templatedatabase 376 containing fingerprint templates and/or fingerprint samples(e.g., fingerprint images) associated with respective users, and/or anaccount database 378 containing account information (e.g., personalinformation, banking information, financial information, funding sourceinformation, etc.), Fingerprint templates of each user may be associatedwith, or included in, the account information of each user. Whilestorage module 374 has been illustrated as located in fingerprintvalidation system 360, one of skill in the art will recognize that itmay include multiple storage modules and may be connected to othermodules through network such as Internet 340 without departing from thescope of the present disclosure. Other modules discussed herein but notillustrated in FIG. 3 may be provided as separate modules on fingerprintvalidation system 360, or using instructions stored on acomputer-readable medium similarly as discussed above.

Fingerprint validation system 360, in various embodiments, may be aseparate hardware server or device or may be provided, at least in part,by venue device 310 and/or service provider server 330.

Venue device 310, user device 320, other mobile devices, serviceprovider server 330, and/or fingerprint validation system 360 cancommunicate with one another via a network, such as Internet 340 or withone another via one or more networks, such as LANs, WANs, cellulartelephone networks, and the like. Venue device 310, mobile devices suchas user device 320, service provider server 330, and other devices cancommunicate with one another, at least partially, via one or more nearfield communications (NFC) methods or other short range communicationsmethods, such as infrared (IR), Bluetooth, WiFi, and WiMax.

When a user wishes to shop for tickets online, resell tickets online,check in at a venue such as an event venue online, access electronictickets online, provide location information online, and/or providefingerprint data online (as examples), the user can open an onlineticket seller's website or can access the ticket seller using anapplication such as app 325. The user can open the ticket seller'swebsite using user device 320, for example. The ticket seller's websitecan be hosted on service provider server 330, venue device 310, or onany other server or device.

An event venue may be any venue for which an attendee can purchaseaccess (e.g., ticketed access) to particular locations or portionswithin the venue for a period of time. Without being limiting examplesof event venues may include a stadium, a theater, an arena, anamphitheater, an airplane, a train, a hotel, or any another venue intowhich an attendee can purchase access.

Referring now to FIG. 4, a diagram 400 of event entrance gates 402(e.g., a venue entrance gate) with fingerprint scan devices 404configured to scan fingerprints is illustrated according to anembodiment. Event entrance gates 402 may be automated entrances gates,such as automated turnstile entrance gates. Fingerprint scan devices 404may be an implementation of fingerprint scan device 314 in FIG. 3. Eachfingerprint scan device 404 may comprise a fingerprint scan area 406,which may be separate from or on the display of fingerprint scan device404. Each fingerprint scan device 404 may be associated with arespective event entrance gate 402.

Referring now to FIG. 5, a flowchart 500 of a method for usingfingerprint recognition for event admission is illustrated according toan embodiment of the present disclosure.

At block 502, fingerprint validation system 360 (e.g., using fingerprintassociation module 362) stores a fingerprint template that is based on afingerprint scan on a user device as a reference fingerprint template.In various embodiments, a user may scan his or her fingerprint usingfingerprint scan module 324 and/or app 325. User device 320 may generatea fingerprint sample (e.g., a fingerprint image) in response to thescan. User device 320 may then transmit fingerprint data to fingerprintvalidation system 360.

In an embodiment, user device 320 may transmit the fingerprint sample tofingerprint validation system 360. Fingerprint validation system 360 maygenerate a fingerprint template by extracting features from thefingerprint sample, and store the fingerprint template associated withthe user as a reference template in template database 376 of storagemodule 374.

In another embodiment, user device 320 may generate a fingerprinttemplate by extracting features from the fingerprint sample, andtransmit the fingerprint template to fingerprint validation system 360.Fingerprint validation system 360 may store the fingerprint templateassociated with the user as a reference template in template database376 of storage module 374.

At block 504, fingerprint validation system 360 (e.g., using ticketassociation module 364) associates the user with a purchased ticket inresponse to the user purchasing the ticket. In an embodiment, the usermay use user device 320 to view, select, and purchase a ticket for anevent on a service provider website hosted by service provider server330 or using a service provider application such as app 325. Serviceprovider server 330 may process a transaction for the purchase of theticket. Fingerprint validation system 360 may receive and/or access theticket purchase information (e.g., from service provider server 330) andstore an association between the purchased ticket and the user inaccount database 378 of storage module 374.

In another embodiment, fingerprint validation system 360 associatesanother user with the ticket purchased by the user. For example, theother user may have received the ticket as a gift from the purchasinguser, bought the ticket from the purchasing user, traded for the ticketfrom the purchasing user, had the ticket purchased by the purchasinguser on the other user's behalf, or ways to acquire the ticket purchasedby the user. The purchasing user may identify the other user, such as byentering a user identifier (e.g., name, phone number, email address,etc.). Fingerprint validation system 360 may then access a database,account, or other source to match the user identifier with a storedfingerprint corresponding to the user identifier. If no storedfingerprint is found, the other user may be notified, such as by phonecall, email, or text, and requested to provide a fingerprint sample,such as described herein.

At block 506, fingerprint validation system 360 (e.g., using comparisonmodule 366) compares a fingerprint template that is based on afingerprint scan on a fingerprint scan device 314 located at an entrancefor the event (e.g., an entrance to the event venue) with referencefingerprint templates. Fingerprint validation system 360 may search fora match among the reference fingerprint templates and/or generatematching scores for each comparison.

At block 508, fingerprint validation system 360 (e.g., using validationmodule 368) validates that the user (or person having his/herfingerprint scanned at the event) is associated with the purchasedticket based on the comparison. In an embodiment, fingerprint validationsystem 360 validates the user by identifying and/or authenticating theuser based on the comparison. In certain embodiments, fingerprintvalidation system 360 may compare the fingerprint template withfingerprint templates of a plurality of users who each purchased aticket for the event to which the user is seeking admission.

In an embodiment, fingerprint validation system 360 may determine amatching score for each comparison and identify user as one of theplurality of users based on determining one of the matching scores beingabove a predetermined threshold.

At block 510, fingerprint validation system 360 (e.g., using accessmodule 370) grants the user access to the event based on the validation.In an embodiment, fingerprint validation system 360 transmits an accessgranting signal to an automated entrance gate (e.g., gate 402 of FIG. 4)associated with the fingerprint scan device 314 at which the userscanned his or her fingerprint. For example, the automated entrance gate(e.g., automated turnstile entrance gates) may move or turn a part ofthe gate, or allow the user to move or turn a part of the gate, so thatthe user may pass through.

In some embodiments, the user may have purchased a plurality of ticketsfor the user and one or more other users. Based on a fingerprint scan bythe user on the fingerprint scan device, fingerprint validation system360 may grant access to the user and also the one or more other users(e.g., by counting the number of users passing through and allowing aplurality of users pass through corresponding to the number of ticketspurchased). Accordingly, the fingerprint template of the user may beassociated with the transaction for the purchase of multiple tickets,and the validation of one user may allow a plurality of users to enterthe event.

Referring now to FIG. 6, a flowchart 600 of a method for using remotefingerprint recognition for event admission is illustrated according toan embodiment of the present disclosure.

At block 602, fingerprint validation system 360 (e.g., using fingerprintassociation module 362) stores a fingerprint template that is based on afingerprint scan on a user device as a reference fingerprint template,as described at block 502 in FIG. 5.

At block 604, fingerprint validation system 360 (e.g., using ticketassociation module 364) associates the user with a purchased ticket inresponse to the user purchasing the ticket, as described at block 504 inFIG. 5. The user may have bought the ticket for another user. The usermay tell the other user that the user has bought a ticket for the otheruser. The user advantageously does not have to give the other user aphysical ticket (e.g., a paper ticket) or electronically send proof ofpurchase of the ticket (e.g., an electronic ticket). The user merely hasto let the other user know, which is convenient for both users.

At block 606, fingerprint validation system 360 receives user identifierinformation for the user and the other user. In an embodiment, the otheruser enters the user identifiers on fingerprint scan device 314. Theuser identifier for the user may include a phone number, an emailaddress, a username, or other user identifier stored with fingerprintvalidation system 360 and/or service provider server 330. The useridentifier for the other user who seeks admission into the event mayinclude a name or any identifier that the user would recognize as beingfrom the other user. As such, when the user receives the user identifierfor the other user, the user can be sure that the person at the entrancewho is trying to use the ticket purchased by the user is the other user.

At block 608, fingerprint validation system 360 (e.g., usingnotification module 365) sends a notification, which may include arequest for approval and/or validation, to user device 320 of the user.In various embodiments, fingerprint validation system 360 may determinea user account using the user identifier for the user by searchingaccount database 378. Fingerprint validation system 360 may thendetermine whether the user associated with the user account isassociated with a purchased ticket for the event. Fingerprint validationsystem 360 may transmit a notification to the user via user device 360.The notification may include the user identifier of the other user(e.g., a name, nickname, phone number, an email address, or otherinformation that would allow the user to determine the other user is atthe entrance) and a request for the user to approve the other user's useof the ticket. In an embodiment, user may approve by validating that theuser holding user device 320 is associated with the purchased ticket byproviding a fingerprint scan on user device 320. In other embodiments,the user may approve without providing further validation (e.g.,providing a fingerprint scan), such as by entering a “approve” button.

At block 610, fingerprint validation system 360 (e.g., using comparisonmodule 366) compares a fingerprint template that is based on afingerprint scan on user device 320, which may be located remotely fromthe entrance for the event, with one or more reference fingerprinttemplates. In an embodiment, fingerprint validation system 360 maycompare a fingerprint template based on a fingerprint scan on userdevice 320 with reference templates by searching for a match among thereference fingerprint templates and/or generating matching scores foreach comparison. In other embodiments, fingerprint validation system 360compares the fingerprint template that is based on a fingerprint scan onuser device 320 with a stored reference template of the user, which maybe determined, for example, based on the user identifier for the userprovided by the other user.

At block 612, fingerprint validation system 360 (e.g., using validationmodule 368) validates that the user is associated with the purchasedticket based on the comparison, as described at block 508 in FIG. 5.

At block 614, fingerprint validation system 360 (e.g., using accessmodule 370) grants the other user access to the event based on theapproval and/or the validation. In an embodiment, fingerprint validationsystem 360 transmits an access granting signal to an automated entrancegate associated with the fingerprint scan device 314 at which the otheruser entered the user identifiers.

Although the foregoing invention has been described in detail by way ofillustration and example for purposes of clarity and understanding, itwill be recognized that the above described invention may be embodied innumerous other specific variations and embodiments without departingfrom the spirit or essential characteristics of the invention. Variouschanges and modifications may be practiced, and it is understood thatthe invention is not to be limited by the foregoing details, but ratheris to be defined by the scope of the claims.

What is claimed is:
 1. A system, comprising: a fingerprint validationsystem, including: an association module configured to transmit anotification to a user device of a first user, the notificationincluding a request for approval of a second user to use a purchasedticket associated with the first user to enter an event in response toreceiving a user identifier for the first user, wherein the request forapproval includes a request to provide a fingerprint scan by the firstuser on the user device; a comparison module configured to compare thefingerprint scan of the first user with a stored reference fingerprinttemplate of the first user; and an access module configured to grant asecond user access to the event when the fingerprint scan matches thestored reference fingerprint template; and a fingerprint scan deviceassociated with a venue of the event, the fingerprint scan deviceconfigured to receive the user identifier entered on the fingerprintscan device by the second user.
 2. The system of claim 1, wherein thenotification further includes a user identifier for the second userentered on the fingerprint scan device.
 3. The system of claim 1,further comprising a fingerprint association module configured to storethe reference fingerprint template associated with a previousfingerprint scan of the first user.
 4. The system of claim 3, whereinthe fingerprint association module receives the reference fingerprinttemplate from the user device.
 5. The system of claim 4, wherein thefingerprint association module receives the previous fingerprint scanfrom the user device and generates the reference fingerprint template byextracting features from the fingerprint scan.
 6. The system of claim 3,further comprising a ticket association module configured to associatethe first user with the purchased ticket to the event in response to thefirst user purchasing the ticket.
 7. The system of claim 4, furthercomprising a validation module configured to validate the first user isassociated with the purchased ticket based on the comparison.
 8. Thesystem of claim 1, wherein the fingerprint scan device is associatedwith an automated entrance gate at the entrance, and wherein the accessmodule is configured to grant access to the event by transmitting anaccess granting signal to the fingerprint scan device or the automatedentrance gate.
 9. A processor-implemented method, comprising:performing, by a first processor, the operations of: transmitting anotification to a user device of a first user, the notificationincluding a request for approval of a second user to use a purchasedticket associated with the first user to enter an event in response toreceiving a user identifier for the first user, wherein the request forapproval includes a request to provide a fingerprint scan by the firstuser on the user device; comparing the fingerprint scan of the firstuser with a stored reference fingerprint template of the first user; andgranting a second user access to the event when the fingerprint scanmatches the stored reference fingerprint template; and receiving, by afingerprint scan device coupled to the first processor, the useridentifier entered by the second user.
 10. The processor-implementedmethod of claim 9, wherein the notification further includes a useridentifier for the second user entered on the fingerprint scan device.11. The processor-implemented method of claim 9, further comprisingstoring the reference fingerprint template associated with a previousfingerprint scan of the first user.
 12. The processor-implemented methodof claim 11, further comprising receiving the reference fingerprinttemplate from the user device.
 13. The processor-implemented method ofclaim 12, further comprising receiving the previous fingerprint scanfrom the user device and generating the reference fingerprint templateby extracting features from the fingerprint scan.
 14. Theprocessor-implemented method of claim 11, further comprising associatingthe first user with the purchased ticket to the event in response to thefirst user purchasing the ticket.
 15. The processor-implemented methodof claim 12, further comprising validating the first user is associatedwith the purchased ticket based on the comparison.
 16. Theprocessor-implemented method of claim 9, further comprising grantingaccess to the event by transmitting an access granting signal to thefingerprint scan device or an automated entrance gate.
 17. Aprocessor-implemented method, comprising: storing reference fingerprinttemplates associated with respective users; storing a first fingerprinttemplate of a first user as one of the reference fingerprint templates,wherein the first fingerprint template is based on a first fingerprintscan on a user device; associating the first user with a purchasedticket to an event in response to the first user purchasing the ticket;transmitting a notification to a user device of the first user, thenotification including a request for approval of a second user to usethe purchased ticket associated with the first user to enter the eventin response to receiving a user identifier for the first user, whereinthe request for approval includes a request to provide a fingerprintscan by the first user on the user device; comparing a secondfingerprint template of the first user with the reference fingerprinttemplates, wherein the second fingerprint template is based on a secondfingerprint scan on a fingerprint scan device at an entrance for theevent; validating the first user is associated with the purchased ticketbased on the comparison; and granting access to the event based on thevalidation.
 18. The processor-implemented method of claim 17, furthercomprising comparing the first fingerprint template with the referencefingerprint templates by determining a matching score, and identifyingthe first user based on the matching score being above a predeterminedthreshold.
 19. The processor-implemented method of claim 17, furthercomprising receiving ticket purchase information for the purchasedticket from a service provider server.
 20. The processor-implementedmethod of claim 17, wherein the granting access further comprisesgranting access to the event to a plurality of users based on thevalidation.